Methods and systems for electronic checklist data references

ABSTRACT

Disclosed are methods, systems, and non-transitory computer-readable medium for electronic checklist data references. For instance, the method may include: displaying, in a GUI, a checklist GUI corresponding to a checklist of an electronic checklist system; determining whether the checklist includes one or more dynamic data references and/or one or more static data references; in response to determining the checklist includes the one or more dynamic data references, performing a dynamic data reference process to display specific data in the checklist GUI for the one more dynamic data references; and in response to determining the checklist includes the one or more static data references, displaying one or more static data fields in the checklist GUI for the one or more static data references to initiate performing a static data reference process for the one or more static data fields.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This patent application is a continuation of and claims the benefit ofpriority to U.S. application Ser. No. 16/720,430, filed Dec. 19, 2019,the entirety of which is incorporated herein by reference.

TECHNICAL FIELD

Various embodiments of the present disclosure relate generally tomethods and system for electronic checklist data references and, moreparticularly, to methods and system for electronic checklist datareferences for avionics checklists.

BACKGROUND

Aircraft checklists (and vehicle checklists in general) may containreferences to data sources that are not contained in the checklist stepsor notes, where the data may be most relevant. For instance, the datamay be found somewhere else in the cockpit (or navigation controlinterface, in general) and the data may be static or dynamic. As anexample, the data could be located inside a reference manual, on a quickreference card, in system synoptics, in a trip planning application of atablet device (e.g., electronic flight bag); therefore, in general, thedata may be in any place that is not the checklist itself. This maycause the crew to search for the data outside the checklist. Forinstance, the process of searching for the data may result in lookingacross the cockpit at different displays than the one display displayingthe checklist, or finding a reference manual that may not be easy toreach. These types of actions may increase crew cognitive and physicalworkload due to visual switching of attentional resources betweenseparate sources of static and dynamic information. Therefore, there maybe a challenge in reducing crew cognitive and physical workload.

Moreover, these types of actions may also increase a potential for errortransference during a referencing action. For instance, a crew membermay incorrectly remember the data or introduce transcription errors forcorrectly remembered data. Furthermore, crew interruptions (e.g., ATCrequests, flight attendant requests, changes in flight plan, conflictsdue to weather, traffic alerts, etc.) may be a normal part of flightoperations and these crew interruptions may disrupt proceduralawareness, and the disrupted procedural awareness may compound thepotential for error. Therefore, there may be another challenge inreducing potential for error transference during a referencing action.

The present disclosure is directed to overcoming one or more of theseabove-referenced challenges.

SUMMARY OF THE DISCLOSURE

According to certain aspects of the disclosure, systems and methods aredisclosed for electronic checklist data references.

For instance, a method may include receiving a user and/or system inputat a graphical user interface (GUI) for a checklist of an electronicchecklist system of one or more vehicle systems; displaying, in the GUI,a checklist GUI corresponding to the checklist of the electronicchecklist system; determining whether the checklist includes one or moredynamic data references and/or one or more static data references; inresponse to determining the checklist includes the one or more dynamicdata references, performing a dynamic data reference process to displayspecific data in the checklist GUI for the one more dynamic datareferences; and in response to determining the checklist includes theone or more static data references, displaying one or more static datafields in the checklist GUI for the one or more static data referencesto initiate performing a static data reference process for the one ormore static data fields.

A system may include a memory storing instructions; and a processorexecuting the instructions to perform a process. The process may includereceiving a user and/or system input at a graphical user interface (GUI)for a checklist of an electronic checklist system of one or more vehiclesystems; displaying, in the GUI, a checklist GUI corresponding to thechecklist of the electronic checklist system; determining whether thechecklist includes one or more dynamic data references and/or one ormore static data references; in response to determining the checklistincludes the one or more dynamic data references, performing a dynamicdata reference process to display specific data in the checklist GUI forthe one more dynamic data references; and in response to determining thechecklist includes the one or more static data references, displayingone or more static data fields in the checklist GUI for the one or morestatic data references to initiate performing a static data referenceprocess for the one or more static data fields.

A non-transitory computer-readable medium may store instructions that,when executed by a processor, cause the processor to perform a method.The method may include: receiving a user and/or system input at agraphical user interface (GUI) for a checklist of an electronicchecklist system of one or more vehicle systems; displaying, in the GUI,a checklist GUI corresponding to the checklist of the electronicchecklist system; determining whether the checklist includes one or moredynamic data references and/or one or more static data references; inresponse to determining the checklist includes the one or more dynamicdata references, performing a dynamic data reference process to displayspecific data in the checklist GUI for the one more dynamic datareferences; and in response to determining the checklist includes theone or more static data references, displaying one or more static datafields in the checklist GUI for the one or more static data referencesto initiate performing a static data reference process for the one ormore static data fields.

Additional objects and advantages of the disclosed embodiments will beset forth in part in the description that follows, and in part will beapparent from the description, or may be learned by practice of thedisclosed embodiments.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate various exemplary embodiments andtogether with the description, serve to explain the principles of thedisclosed embodiments.

FIG. 1 depicts an exemplary vehicle system environment for displayingelectronic vehicle checklists, according to one or more embodiments.

FIGS. 2 and 3 depict GUIs for exemplary electronic checklists, accordingto one or more embodiments.

FIG. 4 depicts an exemplary block diagram of a system for electronicchecklist data references, according to one or more embodiments.

FIG. 5 depicts a flowchart for a method for electronic checklist datareferences, according to one or more embodiments.

FIGS. 6A-6C depict exemplary GUIs for electronic checklist datareferences, according to one or more embodiments.

FIGS. 7A-7E depict exemplary GUIs for electronic checklist datareferences, according to one or more embodiments.

FIG. 8 depicts an example system that may execute techniques presentedherein.

DETAILED DESCRIPTION OF EMBODIMENTS

Various embodiments of the present disclosure relate generally tomethods and system for electronic checklist data references.

In general, the present disclosure is directed to methods and system forelectronic checklist data references for avionics checklists. Forinstance, a system of the present disclosure may display dynamic datareferences and/or static data references in electronic checklists.Dynamic data references may obtain data from outside the checklist anddisplay the data in a position relevant to the checklist tasks.Meanwhile a static data reference may enable a user to view a relatedreference document and select a value to populate a data field.Therefore, the systems and methods of the present disclosure may reducethe potential for error transference during a referencing action and/orreduce crew cognitive and physical workload. For instance, to reduce thepotential for error transference during a referencing action, thesystems of the present disclosure may populate values for a user insteadof a user remembering/transcribing the value. For instance, to reducecrew cognitive and physical workload, the systems of the presentdisclosure may display particular data within the checklist itselfinstead of outside the checklist, so that the user does not have toleave the checklist GUI interface to refer to the particular data.

While this disclosure describes the systems and methods with referenceto aircraft, it should be appreciated that the present systems andmethods are applicable to checklists of vehicles, including those ofdrones, automobiles, ships, or any other autonomous and/orInternet-connected vehicle.

As shown in FIG. 1 , an exemplary system environment for an electronicchecklist is depicted, according to one or more embodiments.Specifically, FIG. 1 is a fragmentary perspective view illustrating theinside of an exemplary aircraft cockpit 20. Although the context of thefollowing discussion is with respect to GUIs of touch screen displaysused in aircraft, it should be understood that the teachings hereinpertain to touch screen displays used in any type of vehicle including,but not limited to, land based vehicles such as automobiles and trainsas well as watercraft and spacecraft. Additionally, the teachings hereinare not limited to vehicle applications. Rather, the teachings hereinmay also be used together with touch screen displays that are employedin stationary applications such as information kiosks and automaticteller machines as well as with touch screen displays that are hand heldor otherwise not mounted to a surface.

Aircraft cockpit 20 includes an instrument panel 22 positioned to beaccessible from a pilot seat 24 and a copilot seat 26. Instrument panel22 includes various front displays 28 and various control features suchas buttons 30, switches 32, and throttle controls 34. Also mounted oninstrument panel 22 is a control touch screen display 36. Moreover, thefront displays 28 may also be touch screen displays.

One of the front displays 28 or the control touch screen display 36(called herein “vehicle manager touch screen”) may be configured tooperate as a vehicle manager that may display interactive electronicchecklists and/or navigation or other vehicle system data. Specifically,a processor may execute a vehicle manager program (comprised ofinstructions executable by the processor) that causes the vehiclemanager touch screen to display a vehicle manager display. For instance,the vehicle manager display may include one or more GUIs as disclosedherein (or variations thereof), such as GUI 200 and GUI 300 (as depictedin FIGS. 2 and 3 , respectively).

The processor may cause the vehicle manager touch screen to display thevehicle manager display by generating images and transmitting the imagesto the vehicle manager touch screen to be displayed. Alternatively, theprocessor may generate instructions and information and transmit theinstructions and information to a graphics processing unit (GPU). TheGPU may generate the images to be displayed on the vehicle manager touchscreen. The vehicle manager program may be stored in a memory. Thememory may be connected to the processor so that the processor mayreceive stored instructions or data, and the processor may process theinstructions, stored data, and received information, in accordance withthe vehicle manager program. The memory and the processor may beconnected to the vehicle manager touch screen either directly orindirectly. Collectively the memory, the processor, and the vehiclemanager touch screen may be referred to as a “vehicle manager system.”In one embodiment, the vehicle manager system may be an electronicprocedure system of a vehicle.

For instance, the vehicle manager program may control a functionalityand configuration of the vehicle manager touch screen, in accordancewith a loadable checklist control file (called herein a “loadabledatabase”), e.g., received from a cloud service. The vehicle managerprogram may store the loadable database in the memory. The vehiclemanager program may control the configuration of the vehicle managertouch screen, based on user inputs to the system, data from othervehicle systems, and/or FMS data from, e.g., a cloud FMS. Specifically,the vehicle manager program may display the vehicle manager display todepict an electronic checklist in accordance with the loadable database,and receive user inputs to view and/or to change the configuration ofthe vehicle manager touch screen.

Generally, user inputs may be a touch interaction with the vehiclemanager touch screen (e.g., capacitive, resistive, and/or opticalsensing), a user input on a keyboard, a mouse, a scroll wheel, or anyother system-defined manner of selecting and interacting with thesystem. The processor may receive the user inputs and perform specificactions based on the user inputs, in accordance with the vehicle managerprogram.

FIGS. 2 and 3 depict exemplary GUIs for an electronic checklist,according to one or more embodiments. Specifically, FIGS. 2 and 3 maydepict a functionality and configuration of the vehicle manager touchscreen, in accordance with a loadable database received from a cloudservice.

In FIG. 2 , GUI 200 may include a group of home icons (including one ormore of a system function menu icon 205, an index icon 210, a reset icon215, a skip icon 220, an ignore icon 225, a display control drop downmenu icon 230), one or more completed task indicators 235, one or morepartially completed task indicators 240 and 245, one or more incompletetask indicators 250, a header 255, a scroll bar indicator 260, and oneor more task titles 265. A processor, as described above, may cause GUI200 to be displayed on the vehicle manager touch screen of the system.The GUI 200 may be a home menu for a vehicle manager system. One or moretasks (a task may be an indicator associated with a task title) mayrepresent a sub-checklist. A user may select the task, and the sub-checklist corresponding to the selected task may be displayed; for instance,FIG. 3 may depict an example of a sub-check list that is displayed inGUI 300. In each checklist (parent checklist), any task may represent asub-checklist of the parent checklist (e.g., a sub-check list to asub-checklist is a grandchild to the home menu).

In FIG. 3 , the GUI 300 may include the same features as the GUI 200,however it may also be different, and it may include a different header255 a, one or more system completed task indicators 305, one or moreignored task indicators 310, one or more challenge instructions 315, oneor more response instructions 320, and one or more additionalinformation indicators 325. Specifically, as mentioned above, when auser selects a task with a sub-checklist, the processor may update thedisplay to display the sub-checklist. The different header 255 a maycorrespond to the task title 265 associated with the selected task (or asub-checklist name if different than the task title 265). The one ormore challenge instructions 315 and the one or more responseinstructions 320 may each be associated with an indicator. The one ormore challenge instructions 315 may contain text associated with thetask the user is to focus attention on. The one or more responseinstructions 320 may contain text associated with the task the crew isto the focus on. The one or more additional information indicators 325may be checklist impact notifications (CINs). The one or more additionalinformation indicators 325 may be associated with tasks that haveadditional information related to notes, cautions, and warnings. CINsmay provide access to notes, cautions, and warnings for individual tasksby a message popup.

FIG. 4 depicts an exemplary block diagram of a system 400 for electronicchecklist data references, according to one or more embodiments. Thesystem 400 may include a cloud service 401 and/or a vehicle 403. Thecloud service 401 and the vehicle 403 may communicate over a networkusing, e.g., a TCP/IP communication infrastructure, or the cloud service401 and the vehicle 403 may communicate over the network and/orsatellite communications infrastructure, etc.

The cloud service 401 may include a cloud flight management system (FMS)440 and/or other software as a service (SaaS) systems. The cloud FMS 440may be a cloud-based platform that provides FMS services to any user whohas authorized access to the cloud FMS 440. Specifically, the cloud FMS440 may provide FMS micro-services. The FMS micro-services may be FMSservices organized as a collection of specialized modular services. Insome implementations, the FMS micro-services may be softwareapplications stored, at least in part, in one or more servers remotefrom the vehicle 403, for cloud-based access from the vehicle 403. TheFMS micro-services may be modular services which are developed,deployed, and scaled independently of each other, messaging-enabled tocommunicate with various components within the cloud FMS 440, andorganized around capabilities. The FMS micro-services may include, forexample, flight planning services, in-flight navigation services,airport specific services, ground communication services, weatherservices, services for computing fuel scenarios, services for computingoptimization scenarios, services for offsetting deviations, and servicesfor computing approach procedures. The FMS micro-services may beimplemented as hardware, software, and/or a combination of hardware andsoftware.

The vehicle 403 may include a vehicle management system 420 and vehiclesystems 430. In one embodiment, the vehicle management system 420 may bean electronic procedure system of a vehicle. The vehicle managementsystem 420 may include a checklist system 422, a mission manager system424, and/or a configuration memory 423 storing configuration data and/oraircraft profile management (APM) data. The configuration data mayinclude configuration rules that generally apply to checklists and/ordisplay of information. The APM data may include additionalconfiguration rules specific to different aircraft defined by originalequipment manufacturers (OEM). The vehicle systems 430 may include oneor more communications system(s) 432 and other systems and sensors 434.

The one or more communications system(s) 432 may include one or more ofa cellular communications system, a Wi-Fi system, a radio communicationssystem, a satellite communications system, etc. The one or morecommunications system(s) 432 may receive and transmit messages to/fromthe vehicle 403 from/to the cloud 401 (e.g., the cloud FMS 440). The oneor more communications system(s) 432 may also communicate with thevehicle management system 420. For instance, the one or morecommunications system(s) 432 may receive FMS data from the cloud FMS440, and transmit the FMS data to the vehicle management system 420.

The other systems and sensors 434 may include one or more of navigationsystems (e.g., GPS systems), engine systems, actuation systems, controlsystems, temperature systems, life systems, external sensors (e.g.,weather radar, temperature, pressure, density, velocity sensors) orinternal sensors (e.g., cabin pressure sensor), etc. of the vehicle 403.The other systems and sensors 434 may communicate with the vehiclemanagement system 420. For instance, the other systems and sensors 434may transmit vehicle systems data to the vehicle management system 420.

The checklist system 422 may communicate with the configuration memory423, the mission manager system 424, and/or the other systems andsensors 434. The checklist system 422 may receive a loadable databasefrom a checklist designer system hosted by, e.g., the cloud FMS 440. Thechecklist system 422 may also receive messages from the mission managersystem 424; the configuration/APM data from the configuration memory423; and the vehicle systems data of the other systems and sensors 434.The checklist system 422 may output checklists GUIs and/or informationfor checklist GUIs to the mission manager system 424, for displayingchecklist GUIs by the mission manager system 424, in accordance with theloadable database, the messages, the configuration/APM data, and thevehicle systems data.

For instance, the checklist system 422 may extract one or more datastructure(s) and one or more function(s) from the loadable database;extract rulebook rules from a rulebook (e.g., included in the loadabledatabase); extract data from databases of the vehicle 403; extractconfiguration rules from the configuration/APM data; extract sensor dataand/or synoptic data from vehicle systems data; extract notificationsfrom the messages from the mission manager system 424 (e.g., a selectionbased on user inputs or a crew alerting system (CAS) message); andextract phase of flight information from messages from the missionmanager system 424 (collectively, “checklist inputs”). The checklistsystem 422 may validate the checklist inputs, e.g., to ensure correctsource(s), correct format, etc.

As discussed above, the loadable database may include the one or morefunction(s) and the one or more data structure(s) for generation andcontrol of the checklist GUIs. Specifically, a data structure mayinclude content and arrangement information. The content may bedisplayed in a checklist GUI in accordance with arrangement information.The configuration rules of the configuration/APM data may includedisplay rules for how the content is to be displayed in accordance withthe arrangement information. A function may include program code for howsystem and/or user inputs are to update the checklist GUI (e.g., asoutputs).

For instance, the one or more data structure(s) may include informationabout minimum equipment lists (MELs), master MELs (MMELs), aircraftflight manuals (AFMs), configuration deviation lists (CDLs), etc. Theprogram code of the one or more function(s) may control checklist GUIsand data based on events. Events may be based phase of flight, CASmessages, flight plan data, flight data, synoptics, and/or pilotaction(s). For example, a function may start based on a phase of flightevent (e.g., transition between takeoff and cruise), and the functionmay generate and display a first checklist GUI corresponding to one ormore tasks for the transition from takeoff to cruise. As anotherexample, a function may start based on an emergency event (e.g.,information indicating a sensor detecting smoke, which may be includedin the vehicle systems data), and generate and display a secondchecklist GUI corresponding to one or more tasks for resolving theemergency event. As discussed above, the checklist GUIs may be based onthe one or more data structure(s), the configuration/APM data, and/orthe one or more function(s).

The mission manager system 424 may communicate with the checklist system422, the configuration memory 423, the other systems and sensors 434,and the cloud FMS 440 (via, e.g., the one or more communications systems432). The mission manager system 424 may receive messages from thechecklist system 422 (e.g., information/instructions/graphics fordisplaying the checklist GUI); the configuration/APM data from theconfiguration memory 423; the vehicle systems data of the other systemsand sensors 434; and/or the FMS data from the cloud FMS 440.

The mission manager system 424 may manage MEL data, manage flight planbuffer and/or display, and/or manage checklist display and interactionsfrom a user, such as a crew of an aircraft. Specifically, the missionmanager system 424 may display one or more of the checklist GUIs, andreceive and process user inputs. For instance, the mission managersystem 424 may render GUIs for managing phase of flight basedchecklists, GUIs for managing CAS/emergency checklists, and/or GUIs foraircraft configurations, and manage crew selections with respect to therendered GUIs. For instance, the mission manager may render the GUIs, asbased on the messages from the checklist system 422; theconfiguration/APM data from the configuration memory 423; the vehiclesystems data of the other systems and sensors 434; and/or the FMS datafrom the cloud FMS 440.

In one aspect of the disclosure the checklist system 422 may perform adata reference process, in accordance with the loadable database. Thedata reference process may include: receiving a user and/or system inputat a graphical user interface (GUI) for a checklist of an electronicchecklist system of one or more vehicle systems; displaying, in the GUI,a checklist GUI corresponding to the checklist of the electronicchecklist system; determining whether the checklist includes one or moredynamic data references and/or one or more static data references; inresponse to determining the checklist includes the one or more dynamicdata references, performing a dynamic data reference process to displayspecific data in the checklist GUI for the one more dynamic datareferences; and in response to determining the checklist includes theone or more static data references, displaying one or more static datafields in the checklist GUI for the one or more static data referencesto initiate performing a static data reference process for the one ormore static data fields.

To receive a user and/or system input at the GUI for the checklist ofthe electronic checklist system of one or more vehicle systems, themission manager system 424 may: receiving a user input on the vehiclemanager touch screen selecting a checklist and/or a system input to themission manager system 424 selecting the checklist. For instance, a usermay select a task by a touch input of the one or more partiallycompleted task indicators 240 of FIG. 2 to display a correspondingsub-checklist (e.g., a “Before Takeoff” sub-checklist). Additionally oralternatively, a system input, such as a CAS message or emergencycondition, may trigger a selection of corresponding checklist for theCAS message or the emergency condition. The mission manager system 424may then transmit the selection of the checklist to the checklist system422.

To be displayed in the GUI, the checklist GUI corresponding to thechecklist of the electronic checklist system may include: receiving, bythe checklist system 422, the selection of the checklist; extracting, bythe checklist system 422, relevant data for the checklist; andtransmitting, by the checklist system 422 to the mission manager system424, the relevant data so that the mission manager system 424 maydisplay the checklist GUI on the vehicle manager touch screen. Themission manager system 424 may then display the checklist GUI on thevehicle manager touch screen. One of skill in the art would recognizethat the mission manager system 424 and the checklist system 422 may bephysically separate systems, logically separate software programs on asame system, or portions of a software program of the vehicle managementsystem 420.

The extracting, by the checklist system 422, the relevant data for thechecklist may include: obtaining checklist function(s) (if any) andchecklist data structure(s) from the one or more function(s) and the oneor more data structure(s) from the loadable database. For instance, theselected checklist may be indicated by an identifier, and the checklistfunction(s) (if any) and checklist data structure(s) may be associatedwith the identifier. The checklist system 422 may find the checklistfunction(s) (if any) and checklist data structure(s) by the associationwith the identifier.

The checklist function(s) may include program code for how the checklistsystem 422 is to manage (e.g., update) the checklist GUI based on userinputs and/or system inputs. For instance, at a minimum, a mainchecklist function may be associated with each checklist to track astate of the checklist as user inputs/system inputs indicate completionof tasks, timers, other system states, etc., and how the completion oftasks, timers, other system, states are to be displayed, in accordancewith content and arrangement information of the checklist datastructure(s). In general, the checklist function(s) for the checklistmay or may not include a data reference function. The data referencefunction may include program code to execute a dynamic data referenceprocess and/or a static data reference process for each dynamic datareference and/or static data reference of a checklist. The datareference function may be executed by the checklist system 422 or themission manager system 424.

To determine whether the checklist includes the one or more dynamic datareferences and/or the one or more static data references, the datareference function may: determine whether the content of the checklistdata structure(s) includes one or more data reference tags; in responseto determining the content of the checklist data structure(s) includesthe one or more data reference tags, for each data reference tag,determine a type of the data reference tag (e.g., dynamic type or statictype); in response to determining the type of each data reference tag,determine the checklist includes the one or more dynamic data referencesand/or the one or more static data references.

The data reference tags may be elements of content for specificchecklist tasks. For instance, as discussed in further detail in FIGS.6A-6C and FIGS. 7A-7E, the elements of content for the data referencetags of the content for various checklist tasks may indicate to the datareference function to execute a specific process (e.g., dynamic datareference process and/or a static data reference process). Each datareference tag may include a one or more display contents, a type (staticor dynamic, which controls a type of functionality of the data referencefunction), one or more pointers corresponding to the one or more displaycontents (e.g., to a resource outside the checklist system 422/missionmanager system 424), and/or fetch data/linked function pointer. As aspecific example, the checklist data structure(s) may be XML code, andthe data reference tag may be an element of a checklist task portion ofthe XML code. The element may include display content, a type attribute,a pointer content, and/or a fetch data content/linked function pointer.The display content may include text to be displayed that is dynamicand/or static, such as “<ref> psi” where “<ref>” is dynamic and is to beupdated and “psi” is static. The type attribute may indicate static ordynamic. The pointer content is an indicator/link to where “<ref>” is tobe obtained (e.g., from outside the checklist system 422). For dynamicdata reference tags, the element may include the fetch data content,which may be an indicator (e.g., at launch) or a rate (e.g., every setperiod of time), and a linked function pointer, which may indicate anassociated function, if any, to be invoked; for static data referencetags, the element may include the linked function pointer, which mayindicate an associated function, if any, to be invoked.

Generally, the pointer(s) (or the pointer content of the XML exampleabove) may be indicators of specific aircraft system bits of informationor links to specific locations for the specific aircraft system bits ofinformation. Examples of aircraft system bits of information may includestatic references and real-time references. Static references mayinclude reference manuals, a quick reference card, PDFs, documents, etc.Real-time references may include system synoptics, EFS data, etc., suchas: (1) CAS messages; (2) environmental control system (ECS) data, suchas pressurization data, cabin altitude data, aircraft altitude data,oxygen data, cabin temperature data, ECS deltas data, vent statuses; (3)performance data and air data system information, such as engine(s)data, fuel data, weight data, boost pump and valve statuses, etc.; (4)hydraulics, flight controls, and configuration devices statuses/data,such as parking and speed brakes statuses/data, doors statuses/data,gear statuses/data, slats statuses/data, and flaps statuses/data; (5)electrical & accessory data, such as statuses of batteries andgenerators, status of emergency locator transmitters (ELT), status ofram air turbine (RAT), status of auxiliary power units (APUs), andstatuses of interior and exterior lights; (6) aircraft capabilities andlimitations data, such as speed data, altitude data, maneuveringlimitations data, approach minimums data, etc.; (7) computer networkdata, such as on-board computer network data, such as from a connecteddevice (e.g., an EFB), and/or off-board network data, such as the FMSdata, etc.; (8) Icing protection data, such as wing anti-ice data, cowlanti-ice data, windshield heat data, leading edge boots data; and/or (9)aircraft location status: aircraft on ground status and/or weight onwheel status.

Generally, the data reference function may be passed the data referencetags, and perform the dynamic data reference process for each dynamicdata reference tag and/or display one or more static data fields in thechecklist GUI for the one or more static data references to initiateperforming a static data reference process for the one or more staticdata fields. Specifically, the data reference function may, for eachdata reference tag, obtain a type of the data reference tag; determinewhether the type is a dynamic type or a static type; in response todetermining the type is a dynamic type, execute a dynamic data referenceprocess for that data reference tag; and in response to determining thetype is a static type, display a static data fields in the checklist GUIfor the static data reference to initiate performing a static datareference process for the static data field.

To perform the dynamic data reference process to display specific datain the checklist GUI for the one more dynamic data references, the datareference function may (for each dynamic data reference tag): obtain apointer and/or a fetch data from a data reference tag; obtain particulardata based on the pointer; display the particular data in accordancewith the display content; determine whether the fetch data indicates atlaunch (e.g., 1 time) or a rate; in response to determining the fetchdata indicates at launch, end the process; and in response todetermining the fetch data is a rate, obtain the particular data everyset period of time in accordance with the rate. To obtain particulardata based on the pointer, the data reference function may (1) filterreceived data (e.g., received by the mission manager system 424 or thechecklist system 422) to obtain a corresponding aircraft system bit ofinformation, and/or (2) transmit a request to a system component of theother systems and sensors 434 and receive a response from the systemcomponent that includes the corresponding aircraft system bit ofinformation. As one of skill in the art would recognize, the dynamicdata reference process is dynamic because the checklist may not containthe particular data to be displayed until the data reference functionobtains the particular data and displays the particular data. In thismanner, the methods and systems of the present disclosure may referencedata outside the checklist system 422 or the mission manager system 424,in accordance with the pointer and the fetch data. Moreover, in the casethe fetch data is a rate, the dynamic process may continuously updatethe particular data so that a user is informed of changes in theparticular data.

To display the one or more static data fields in the checklist GUI forthe one or more static data references to initiate performing a staticdata reference process for the one or more static data fields, the datareference function may: obtain the display content (which may dictatethe content and arrangement of the static data fields); and display thedisplay content in the checklist GUI, until a user input/system inputselects the static data fields to initiate performing a static datareference process. To perform the static data reference process, thedata reference function may (for each static data reference tag): waitfor a user input/system input on a static data field; in response to theuser input/system input selecting the static data field, launch a viewerbased on a pointer of a corresponding static data reference tag; inresponse to user input(s) on the viewer, populate the static data fieldwith a value; and invoke an associated function, if any, based on alinked function pointer (of the checklist function(s)) using the value.A user input selecting the static data field may be a touch, click, etc.on an associated task of the static data field or on the static datafield itself. A system input selecting the static data field, may be auser input/system input indicating a task preceding (e.g., immediatelypreceding) the task associated with the static data field is complete.

To launch the viewer based on the pointer of the corresponding staticdata reference tag, the data reference function may: access acorresponding data reference (e.g., reference manuals, a quick referencecard, PDFs, documents) using the pointer; and display a portion of thedata reference (e.g., by opening the data reference to a page, section,chart, etc., in accordance with the pointer). The data referencefunction may then select a value based on user inputs (e.g., asdiscussed below with respect FIGS. 7A-7E). In response to user input(s)on the viewer, the data reference function may then populate the staticdata field with the value. In response to the value being populated, thedata reference function may then invoke the associated function, if any,based on a linked function pointer by passing the value in a call to theassociated function. In this manner, the methods and systems of thepresent disclosure may reference data outside the checklist system 422or the mission manager system 424, in accordance with the pointer, andinvoke an associated function, in accordance with the linked functionpointer.

Therefore, the systems and methods of the present disclosure may reducethe potential for error transference during a referencing action and/orreduce crew cognitive and physical workload. For instance, to reduce thepotential for error transference during a referencing action, thesystems of the present disclosure may populate values for a user insteadof a user remembering/transcribing the value. For instance, to reducecrew cognitive and physical workload, the systems of the presentdisclosure may display particular data within the checklist itselfinstead of outside the checklist, so that the user does not have toleave the checklist GUI interface to refer to the particular data.

As an example, a crew may be required to manually control cabin pressureand altitude during a rapid depressurization event. Using the systems ofthe present disclosure, the data reference function may displayreal-time ECS data in a related ECS checklist that is presented with thechecklist step to manually control cabin altitude and then remind thecrew to continually monitor and change the setting. This may lower crewworkload during high-stress conditions where there is high potential forthe crew to forget what the setting is and to take action on theinstruction.

FIG. 5 depicts a flowchart 500 for a method for electronic checklistdata references, according to one or more embodiments. The flowchart 500may be performed by the checklist system 422 and the mission manager424, as discussed above, and whichever of the checklist system 422 andthe mission manager 424 is executing the data reference function. Themission manager system 424 may start the process of the flowchart 500 bydetermining whether user input/system input selects a checklist (block505). For instance, the mission manager system 424 may determine whethera user input selects a task to open a sub-checklist, as discussed abovewith respect to FIG. 4 .

In response to determining that no user input/system input selects achecklist (block 505: No), the mission manager system 424 may proceed towait until the user input/system input selects a checklist (block 505).In response to determining that user input/system input selects achecklist (block 505: Yes), the mission manager system 424 may transmita message to the checklist system 424 indicating the selected checklist,and receive data back to display a checklist GUI corresponding to thechecklist (block 510).

Next, the data reference function may determine whether the checklistincludes the one or more dynamic data references and/or the one or morestatic data references (block 515). For instance, the data referencefunction may determine whether there are one or more dynamic datareference tags and/or one or more static data reference tags, asdiscussed above.

In response to determining that the checklist does not include the oneor more dynamic data references and/or the one or more static datareferences (block 515: No), the data reference function may then exitand return to wait for a user input/system input selecting anotherchecklist (block 505). In response to determining that the checklistdoes include the one or more dynamic data references and/or the one ormore static data references (block 515: Yes): (1) for each dynamic datareference, the data reference function may then perform a dynamic datareference process (block 520); and (2) for each static data reference,the data reference function may display a static data reference (e.g., astatic data field) (block 525).

For instance, for the dynamic data references, the data referencefunction may obtain particular data and display the particular data inaccordance with the pointer and fetch data of the dynamic datareferences, as discussed above. After the checklist is complete (or thefetch data indicates retrieval of particular data once, e.g., only atlaunch), the data reference function may then exit and return to waitfor a user input/system input selecting another checklist (block 505).

In the case static data references are displayed, the data referencefunction may continue to determine whether a user input/system inputselects a static data reference (e.g., a static data field) (block 530).In response to determining that no user input/system input selects astatic data reference (bock 530: No), the data reference function maywait until user input/system input selects a static data reference(block 530). In response to determining that a user input/system inputselects a static data reference (bock 530: Yes), the data referencefunction may then perform a static data reference process (block 530).For instance, the data reference function may, based on user input(s) ona viewer of a data reference displayed based on a pointer of the staticdata reference, populate the static data field with a value; and invokean associated function, if any, based on a linked function pointer, asdiscussed above with respect to FIG. 4 . After the checklist is complete(or associated functions have run), the data reference function may exitand return to wait for a user input/system input selecting anotherchecklist (block 505).

Turning to FIGS. 6A-6C, FIGS. 6A-6C may depict exemplary GUIs forelectronic checklist data references, according to one or moreembodiments. Specifically, FIGS. 6A-6C may depict different arrangementsof display contents and/or invoking associated functions for dynamicdata reference process, in accordance with the data reference functionof FIG. 4 above.

GUI 600A may depict a GUI with an arrangement a plurality of dynamicdata references 605 in associated with a single task of checklist 603.The plurality of dynamic data references 605 may include a first dynamicdata reference 605A, a second dynamic data reference 605B, and a thirddynamic data reference 605C. Each of the first dynamic data reference605A, the second dynamic data reference 605B, and the third dynamic datareference 605C may correspond to a different specific aircraft systembit of information that may inform a user, in associated with a task ofthe checklist 603, of current particular data that may not be includedthe checklist data structure, but instead may be based on data fromoutside the checklist. In this manner, a user may be informed ofrelevant data without having to navigate away from the checklist.

GUI 600B may depict a GUI with an arrangement of a dynamic datareference 615 and instructions 619 combined with a dynamic datareferences 617 in checklist 613. The instructions 619 may be a part ofthe display content for the task associated with the dynamic datareferences 617. The dynamic data reference 617 may include a firstdynamic data reference 617A and a second dynamic data reference 617B,which may be controlled by a user in accordance with instruction 619.

GUI 600C may depict a GUI with an arrangement of a dynamic datareference 625B and an associated function 625A in checklist 623. Theassociated function 625A may be invoked by the data reference functionbased on, e.g., a trigger condition (such as, in this case, deploymentof RAT) and the changes in the particular data may be displayed as thedynamic data reference 625A.

In this manner, the systems of the present disclosure may depict to theuser a GUI that includes coupled data references, as disclosed by theGUI 600A; the systems of the present disclosure may depict to the user aGUI that includes a dynamic data reference coupled with user actioninstruction, as disclosed by the GUI 600B; the systems of the presentdisclosure may depict to the user a GUI that includes an impactassessment based on user actions and/or data readings to inform the userby invoking an associated function, as depicted in GUI 600C.

Turning to FIGS. 7A-7E, FIGS. 7A-7E may depict exemplary GUIs forelectronic checklist data references, according to one or moreembodiments. Specifically, FIGS. 7A-7E may depict a static datareference process to select a value to be populated, in accordance withthe data reference function of FIG. 4 above.

GUI 700A may depict a checklist 705 in a checklist interface 703. Thechecklist 705 may include a static data reference 707 that may be usedto populate a plurality of static data fields 709 with values for anassociated function of the static data reference 707. The plurality ofstatic data fields 709 may include a first static data field 709A, asecond static data field 709D, a third static data field 709C, and afourth static data field 709D, etc. The static data reference 707 andthe plurality of static data fields 709 may selectable by a userinput/system input to initiate a static data reference process, asdiscussed above.

GUI 700B may depict, in response to a user input/system input (asdiscussed above) on the static data reference 707 and/or the pluralityof static data fields 709, a viewer 713. The viewer 713 may displaytitle 715 and a data reference 717. In this case, data reference is achart that includes a plurality of rows 717C intersecting a plurality ofcolumns 717B with values 717A associated with each intersection. Note,however, one of skill in art would recognize that the viewer 713, asdiscussed above, may depict various documents for a user to select avalue to populate the static data field.

GUI 700C may depict a user input sequence 719 to select a value from thestatic data reference 707 of GUI 700B. For instance, as a first example,a user may select a row 719A and a column 719B (in either order) toindicate a value 719C, each of which may by emphasized; alternatively oradditionally, the user may select the value 719C, and the row 719A andcolumn 719B and each of which may be emphasized. The emphasis may be abolded outline (as depicted), but the emphasis may be done in anygeneral manner, such as highlighting an area of the selected items,dimming background of non-selected items, bolding texting, etc. Theemphasis may indicate to the user which row/column/value was selected.In this manner, a user may confirm relationships; in this case, a usermay confirm temperature and weather conditions to populate anappropriate value 719C. The data reference function may then populatethe value 719C in the plurality of static data fields 709, and updatethe GUI 700C to display a plurality of populated data fields 721 (A-D,etc.).

GUI 700D may depict a confirmation menu 723. The confirmation menu 723may be used to confirm that the user is satisfied with the plurality ofpopulated data field 721. The confirmation menu 723 may include cancelelement 725A and a confirm element 725B, each selectable by a user input(e.g., touch or click). The cancel element 725A may exit theconfirmation menu 723 and not proceed to invoke an association functionso that a user may re-select a value 719C to be populated, while theconfirm element 725B may proceed to invoke the associated function withthe currently populated plurality of populated data fields 721.

GUI 700E may depict the associated function 727 after the associatedfunction 727 had been invoked by the date reference function. In thiscase, the associated function 727 may be a timer function, but theassociated function 727 may, in general, be a logic function thatexecutes logical operators (as defined by the program code of theassociated function) on the values passed to the logic function by thedata reference function and/or other data from the other systems andsensors 434.

FIG. 8 depicts an example system that may execute techniques presentedherein. FIG. 8 is a simplified functional block diagram of a computerthat may be configured to execute techniques described herein, accordingto exemplary embodiments of the present disclosure. Specifically, thecomputer (or “platform” as it may not be a single physical computerinfrastructure) may include a data communication interface 860 forpacket data communication. The platform may also include a centralprocessing unit (“CPU”) 820, in the form of one or more processors, forexecuting program instructions. The platform may include an internalcommunication bus 810, and the platform may also include a programstorage and/or a data storage for various data files to be processedand/or communicated by the platform such as ROM 830 and RAM 840,although the system 800 may receive programming and data via networkcommunications. The system 800 also may include input and output ports850 to connect with input and output devices such as keyboards, mice,touchscreens, monitors, displays, etc. Of course, the various systemfunctions may be implemented in a distributed fashion on a number ofsimilar platforms, to distribute the processing load. Alternatively, thesystems may be implemented by appropriate programming of one computerhardware platform.

The general discussion of this disclosure provides a brief, generaldescription of a suitable computing environment in which the presentdisclosure may be implemented. In one embodiment, any of the disclosedsystems, methods, and/or graphical user interfaces may be executed by orimplemented by a computing system consistent with or similar to thatdepicted and/or explained in this disclosure. Although not required,aspects of the present disclosure are described in the context ofcomputer-executable instructions, such as routines executed by a dataprocessing device, e.g., a server computer, wireless device, and/orpersonal computer. Those skilled in the relevant art will appreciatethat aspects of the present disclosure can be practiced with othercommunications, data processing, or computer system configurations,including: Internet appliances, hand-held devices (including personaldigital assistants (“PDAs”)), wearable computers, all manner of cellularor mobile phones (including Voice over IP (“VoIP”) phones), dumbterminals, media players, gaming devices, virtual reality devices,multi-processor systems, microprocessor-based or programmable consumerelectronics, set-top boxes, network PCs, mini-computers, mainframecomputers, and the like. Indeed, the terms “computer,” “server,” and thelike, are generally used interchangeably herein, and refer to any of theabove devices and systems, as well as any data processor.

Aspects of the present disclosure may be embodied in a special purposecomputer and/or data processor that is specifically programmed,configured, and/or constructed to perform one or more of thecomputer-executable instructions explained in detail herein. Whileaspects of the present disclosure, such as certain functions, aredescribed as being performed exclusively on a single device, the presentdisclosure may also be practiced in distributed environments wherefunctions or modules are shared among disparate processing devices,which are linked through a communications network, such as a Local AreaNetwork (“LAN”), Wide Area Network (“WAN”), and/or the Internet.Similarly, techniques presented herein as involving multiple devices maybe implemented in a single device. In a distributed computingenvironment, program modules may be located in both local and/or remotememory storage devices.

Aspects of the present disclosure may be stored and/or distributed onnon-transitory computer-readable media, including magnetically oroptically readable computer discs, hard-wired or preprogrammed chips(e.g., EEPROM semiconductor chips), nanotechnology memory, biologicalmemory, or other data storage media. Alternatively, computer implementedinstructions, data structures, screen displays, and other data underaspects of the present disclosure may be distributed over the Internetand/or over other networks (including wireless networks), on apropagated signal on a propagation medium (e.g., an electromagneticwave(s), a sound wave, etc.) over a period of time, and/or they may beprovided on any analog or digital network (packet switched, circuitswitched, or other scheme).

Program aspects of the technology may be thought of as “products” or“articles of manufacture” typically in the form of executable codeand/or associated data that is carried on or embodied in a type ofmachine-readable medium. “Storage” type media include any or all of thetangible memory of the computers, processors or the like, or associatedmodules thereof, such as various semiconductor memories, tape drives,disk drives and the like, which may provide non-transitory storage atany time for the software programming. All or portions of the softwaremay at times be communicated through the Internet or various othertelecommunication networks. Such communications, for example, may enableloading of the software from one computer or processor into another, forexample, from a management server or host computer of the mobilecommunication network into the computer platform of a server and/or froma server to the mobile device. Thus, another type of media that may bearthe software elements includes optical, electrical and electromagneticwaves, such as used across physical interfaces between local devices,through wired and optical landline networks and over various air-links.The physical elements that carry such waves, such as wired or wirelesslinks, optical links, or the like, also may be considered as mediabearing the software. As used herein, unless restricted tonon-transitory, tangible “storage” media, terms such as computer ormachine “readable medium” refer to any medium that participates inproviding instructions to a processor for execution.

The terminology used above may be interpreted in its broadest reasonablemanner, even though it is being used in conjunction with a detaileddescription of certain specific examples of the present disclosure.Indeed, certain terms may even be emphasized above; however, anyterminology intended to be interpreted in any restricted manner will beovertly and specifically defined as such in this Detailed Descriptionsection. Both the foregoing general description and the detaileddescription are exemplary and explanatory only and are not restrictiveof the features, as claimed.

As used herein, the terms “comprises,” “comprising,” “having,”including,” or other variations thereof, are intended to cover anon-exclusive inclusion such that a process, method, article, orapparatus that comprises a list of elements does not include only thoseelements, but may include other elements not expressly listed orinherent to such a process, method, article, or apparatus.

In this disclosure, relative terms, such as, for example, “about,”“substantially,” “generally,” and “approximately” are used to indicate apossible variation of ±10% in a stated value.

The term “exemplary” is used in the sense of “example” rather than“ideal.” As used herein, the singular forms “a,” “an,” and “the” includeplural reference unless the context dictates otherwise.

Other embodiments of the disclosure will be apparent to those skilled inthe art from consideration of the specification and practice of theinvention disclosed herein. It is intended that the specification andexamples be considered as exemplary only, with a true scope and spiritof the invention being indicated by the following claims.

What is claimed is:
 1. A method for electronic checklist datareferences, comprising: receiving a user and/or system input at agraphical user interface (GUI) for a checklist of an electronicchecklist system of one or more vehicle systems; displaying, in the GUI,a checklist GUI corresponding to the checklist of the electronicchecklist system; determining whether the checklist includes one or moredynamic data references and/or one or more static data references,wherein the one or more static data references comprise one or more of:a reference manual; a quick reference card; a pdf file; or a document;in response to determining the checklist includes the one or moredynamic data references, performing a dynamic data reference process todisplay specific data in the checklist GUI for the one more dynamic datareferences; and in response to determining the checklist includes theone or more static data references, displaying one or more static datafields in the checklist GUI for the one or more static data referencesto initiate performing a static data reference process for the one ormore static data fields.
 2. The method of claim 1, wherein thedisplaying the checklist GUI corresponding to the checklist of theelectronic checklist system includes: obtaining checklist function(s)and checklist data structure(s) associated with the checklist from oneor more function(s) and one or more data structure(s) of loadabledatabase associated with the electronic checklist system, the checklistfunction(s) including a data reference function, the data referencefunction including program code to execute the dynamic data referenceprocess and/or the static data reference process for each dynamic datareference and/or static data reference of the checklist; and generatingthe checklist GUI based on the checklist function(s) and checklist datastructure(s).
 3. The method of claim 2, wherein the determining whetherthe checklist includes the one or more dynamic data references and/orthe one or more static data references includes, by the data referencefunction: determining whether a content of the checklist datastructure(s) includes one or more data reference tags; in response todetermining the content of the checklist data structure(s) includes theone or more data reference tags, for each data reference tag,determining a type of the data reference tag; in response to determiningthe type of each data reference tag, determining the checklist includesthe one or more dynamic data references and/or the one or more staticdata references.
 4. The method of claim 3, wherein the data referencetags are elements of content for particular checklist tasks, and eachdata reference tag includes one or more display contents, a type, one ormore pointers corresponding to the one or more display contents, and/orfetch data/linked function pointer.
 5. The method of claim 4, whereinthe one or more pointers are indicators of specific system bits ofinformation or links to specific locations for the specific system bitsof information, the specific system bits of information including staticreferences and real-time references.
 6. The method of claim 5, wherein,for each dynamic data reference, to perform the dynamic data referenceprocess, the method further includes: obtaining a pointer and/or a fetchdata from a data reference tag; obtaining particular data based on thepointer; displaying the particular data in accordance with the displaycontent; determining whether the fetch data indicates at launch or arate; in response to determining the fetch data indicates at launch, endthe dynamic data reference process; and in response to determining thefetch data is a rate, obtaining the particular data every set period oftime in accordance with the rate.
 7. The method of claim 5, wherein toperform the static data reference process for the one or more staticdata fields, the method further includes, for each static data referencetag: waiting for a user input/system input on a static data field; inresponse to the user input/system input selecting the static data field,launching a viewer based on a pointer of a corresponding static datareference tag; in response to user input(s) on the viewer, populatingthe static data field with a value; and invoking an associated functionbased on a linked function pointer using the value.
 8. A system forelectronic checklist data references, the system comprising: a memorystoring instructions; and a processor executing the instructions toperform a process including: receiving a user and/or system input at agraphical user interface (GUI) for a checklist of an electronicchecklist system of one or more vehicle systems; displaying, in the GUI,a checklist GUI corresponding to the checklist of the electronicchecklist system; determining whether the checklist includes one or moredynamic data references and/or one or more static data references,wherein the one or more static data references comprise one or more of:a reference manual; a quick reference card; a pdf file; or a document;in response to determining the checklist includes the one or moredynamic data references, performing a dynamic data reference process todisplay specific data in the checklist GUI for the one more dynamic datareferences; and in response to determining the checklist includes theone or more static data references, displaying one or more static datafields in the checklist GUI for the one or more static data referencesto initiate performing a static data reference process for the one ormore static data fields.
 9. The system of claim 8, wherein thedisplaying the checklist GUI corresponding to the checklist of theelectronic checklist system includes: obtaining checklist function(s)and checklist data structure(s) associated with the checklist from oneor more function(s) and one or more data structure(s) of loadabledatabase associated with the electronic checklist system, the checklistfunction(s) including a data reference function, the data referencefunction including program code to execute the dynamic data referenceprocess and/or the static data reference process for each dynamic datareference and/or static data reference of the checklist; and generatingthe checklist GUI based on the checklist function(s) and checklist datastructure(s).
 10. The system of claim 9, wherein the determining whetherthe checklist includes the one or more dynamic data references and/orthe one or more static data references includes, by the data referencefunction: determining whether a content of the checklist datastructure(s) includes one or more data reference tags; in response todetermining the content of the checklist data structure(s) includes theone or more data reference tags, for each data reference tag,determining a type of the data reference tag; in response to determiningthe type of each data reference tag, determining the checklist includesthe one or more dynamic data references and/or the one or more staticdata references.
 11. The system of claim 10, wherein the data referencetags are elements of content for particular checklist tasks, and eachdata reference tag includes one or more display contents, a type, one ormore pointers corresponding to the one or more display contents, and/orfetch data/linked function pointer.
 12. The system of claim 11, whereinthe one or more pointers are indicators of specific system bits ofinformation or links to specific locations for the specific system bitsof information, the specific system bits of information including staticreferences and real-time references.
 13. The system of claim 12,wherein, for each dynamic data reference, to perform the dynamic datareference process, the method further includes: obtaining a pointerand/or a fetch data from a data reference tag; obtaining particular databased on the pointer; displaying the particular data in accordance withthe display content; determining whether the fetch data indicates atlaunch or a rate; in response to determining the fetch data indicates atlaunch, end the dynamic data reference process; and in response todetermining the fetch data is a rate, obtaining the particular dataevery set period of time in accordance with the rate.
 14. The system ofclaim 12, wherein to perform the static data reference process for theone or more static data fields, the method further includes, for eachstatic data reference tag: waiting for a user input/system input on astatic data field; in response to the user input/system input selectingthe static data field, launching a viewer based on a pointer of acorresponding static data reference tag; in response to user input(s) onthe viewer, populating the static data field with a value; and invokingan associated function based on a linked function pointer using thevalue.
 15. A non-transitory computer-readable medium storinginstructions that, when executed by a processor, cause the processor toperform a method for electronic checklist data references, the methodcomprising: receiving a user and/or system input at a graphical userinterface (GUI) for a checklist of an electronic checklist system of oneor more vehicle systems; displaying, in the GUI, a checklist GUIcorresponding to the checklist of the electronic checklist system;determining whether the checklist includes one or more dynamic datareferences and/or one or more static data references, wherein the one ormore static data references comprise one or more of: a reference manual;a quick reference card; a pdf file; or a document; in response todetermining the checklist includes the one or more dynamic datareferences, performing a dynamic data reference process to displayspecific data in the checklist GUI for the one more dynamic datareferences; and in response to determining the checklist includes theone or more static data references, displaying one or more static datafields in the checklist GUI for the one or more static data referencesto initiate performing a static data reference process for the one ormore static data fields.
 16. The non-transitory computer-readable mediumof claim 15, wherein the displaying the checklist GUI corresponding tothe checklist of the electronic checklist system includes: obtainingchecklist function(s) and checklist data structure(s) associated withthe checklist from one or more function(s) and one or more datastructure(s) of loadable database associated with the electronicchecklist system, the checklist function(s) including a data referencefunction, the data reference function including program code to executethe dynamic data reference process and/or the static data referenceprocess for each dynamic data reference and/or static data reference ofthe checklist; and generating the checklist GUI based on the checklistfunction(s) and checklist data structure(s).
 17. The non-transitorycomputer-readable medium of claim 16, wherein the determining whetherthe checklist includes the one or more dynamic data references and/orthe one or more static data references includes, by the data referencefunction: determining whether a content of the checklist datastructure(s) includes one or more data reference tags; in response todetermining the content of the checklist data structure(s) includes theone or more data reference tags, for each data reference tag,determining a type of the data reference tag; in response to determiningthe type of each data reference tag, determining the checklist includesthe one or more dynamic data references and/or the one or more staticdata references.
 18. The non-transitory computer-readable medium ofclaim 17, wherein the data reference tags are elements of content forparticular checklist tasks, and each data reference tag includes one ormore display contents, a type, one or more pointers corresponding to theone or more display contents, and/or fetch data/linked function pointer.19. The non-transitory computer-readable medium of claim 18, wherein theone or more pointers are indicators of specific system bits ofinformation or links to specific locations for the specific system bitsof information, the specific system bits of information including staticreferences and real-time references.
 20. The non-transitorycomputer-readable medium of claim 19, wherein to perform the static datareference process for the one or more static data fields, the methodfurther includes, for each static data reference tag: waiting for a userinput/system input on a static data field; in response to the userinput/system input selecting the static data field, launching a viewerbased on a pointer of a corresponding static data reference tag; inresponse to user input(s) on the viewer, populating the static datafield with a value; and invoking an associated function based on alinked function pointer using the value.